1 link tagged with all of: claude code + ai + dogfooding + agentic coding + cli
Click any tag below to further narrow down your results
Links
Boris and Cat, the team behind Claude Code, explain how a terminal tool grew out of an internal prototype after an engineer was told to use it instead of hand-writing code. They cover why giving the model bash and a few tools worked better than building a custom toolkit.
- Claude Code began as an internal research tool called Clyde. A new engineer's hand-written PR got rejected with "use Clyde," and the one-shot result convinced the team that an IDE might not be necessary.
- The turning point was giving the model bash. It started writing AppleScript and automating things on its own, which the team had not expected.
- Anthropic "dogfoods" the product: roughly 70 to 80 percent of technical staff use it daily, and internal feedback arrives constantly, so features get shipped or pulled within days.
- The team has been removing tools over time. The LS tool was dropped once bash permissions could enforce directory restrictions, which leaves less clutter in the model's context.